However, others people without buying the DTK, can also include this tag. :P. But it won't work.

List of most recent posts globally. When a developer wants to kill some time, it would be nice to see what people are asking. These forums are based on the Apple Support Communities forums, at least from a technical perspective. Apple Support Communities has a "Subscriptions" feature that would really be useful here. Ability to see all of your responses. We can currently see a count, but not the actual posts. It would be nice to know if someone answered a followup. Apple Support Communities supports this too, albeit a bit awkwardly. Signatures These can be easily abused by spammers. Polls That's a can-o-worms. Not going to happen. Users need to be able to criticize or vent about Apple or Apple products You've got the rest of the internet for that. Can't we have just one safe space where we can talk code and tech without politics? Year-round Apple Engineer engagement. The forums will die/lose respect if we only get serious engagement a few weeks in June. Apple's Developer forums have always had engagement from Apple engineers. And that was when the forums were pretty much a wasteland. If more real developers used the forums as a resource, then I'm sure Apple will devote even more support resources to them.

What do you think about MacEggs.com ?  Never heard of it until you mentioned it. They seem to be trying to capitalize on comments about Apple developer platforms that are popular on social media right now. All I can tell you is to make sure to do good research before entering into any legal agreement. Make sure you know what your rights and responsibilities are. Make sure you know who, specifically, you are entering into an agreement with. Do they have a good reputation? What other apps are using them? How does the licensing work? Who, ultimately, has control over your software and your customers? What sort of infrastructure will you need? Pay particular attention to your responsibilities for sales tax/VAT, privacy regulations, and consumer law. In many jurisdictions, these laws are applicable based on where the customer is located, not where the vendor is located. And who are you, specifically, in that relationship? Are you really the vendor? Or are you, as a developer, something else in some kind of grey area in between? If you use Apple, then you have a lot of institutional support and legal recognition. By that I mean you can tell your accountant, your lawyer, and you government tax agency that your business is selling software through Apple's App Stores and they will understand and know how to deal with it. If you do something else, then make sure to consult with your accountant and lawyer first so that they know what you are doing and can tell you exactly how you need to manage the taxation and legal issues.

You don’t have to use the Mac App Store. There are plenty of low-quality products elsewhere too. However, selling software on the internet is more difficult than it seems. You have to comply with tax, privacy, and consumer laws all over the world. There are even some payment providers like Paddle or Fastpring that handle most of that for you. But you will need to setup your own infrastructure to handle payments, licensing, etc. Due to my own poor choice of projects, I sell in both the Mac App Store and directly. Direct sales are a royal pain. My goal is to be 100% in Apple’s App Stores. Then, all I have to worry about is my app. Apple handles virtually everything else.

You are describing an "app". What you need is to save your main project as a stand-alone workspace. Then, you can add other projects into your workspace. This will create connections between them so you can embed the products from the supporting projects into the main.The only tricky part is setting up the directory structure. All of the project directories need to be siblings. Each project directory will have a project file and yet another directory (maybe more) for source code.

Tthere is no problem with this. This is a classic "free trial". However, you should think of the marketing aspects. If the user can't do anything at all without the subscription, many will dump it after the free trial. If you can offer some free functionality, that will keep them using it and keep them seeing your subscription opportunity. Think of the free functionality as a built-in advertisement.

What's wrong with packagemaker? It was never loved very much, but it works.

You can manually add frameworks (Other linker flags) and search paths (Framework Search paths) in the Build Settings tab.

How can promo codes be considered "mission critical"? They are intended to promote your app. You give them to media and "influencers" so they can use your app and blog about how great it is. Are you trying to use them for something else? You are taking a risk there. There are a lot of open-ended clauses in the developer agreement that let Apple kill your app and your entire developer account if Apple thinks you are engaging in some kind of fraud. I think that risk would be more "mission critical" than the promo codes.

Apple is not asking for permission to use an SDK. Generally Apple assumes that any SDK you manage to acquire, you have rights to use. The only exception is GPL-licensed software which Apple knows is not compatible with Apple's App Stores. However, Zoom is also a service. That is different. You need some kind of agreement with Zoom to use their service. As that is a paid service, you should have said documentation.

That's a bridge panic. I doubt it is related to your extension. Bridge panics often don't generate a report. In theory, the system is supposed to save the panic report in NVRAM and then record it after restarting. But since you are dealing with the embedded version of iOS in a Mac that deals with that kind of low-level behaviour, you may not get the report. See if it is still in NVRAM. You might need to try some 3rd party tools, possibly even some 3rd party OS tools. Some NVRAM values are only accessible if you are running Linux.However, I'm not sure it is worth the effort. Can you positively confirm that your extension is causing the panic? Can you reproduce the panic on demand? Does the panic occur on any individual machine of a certain model? Do you have any 3rd party hardware connected?

Kernel extensions are deprecated.

Probably the standard way is to validate your receipt. As eskimo mentions, this is always an "arms race" against pirates. The trick is to frustrate the pirates so that they spend more effort cracking your app than you do validating it. But it's tricky. If you spend too much effort, then you are working too hard trying to prevent illegitimate use instead of providing value to your current and new customers. Plus, if you ***** it up, then you introduce bugs to those legitimate users. When you deploy apps at scale, sometimes very rare bugs, sometimes operating system bugs, will manifest in your app as piracy attempts. Where possible, try to put functionality or content on a server. Your app will have to request the content from the server using the receipt. You can then validate that receipt easily and securely with Apple. And as a side benefit, this will give you pretty accurate number of how much piracy you are actually seeing.

There aren't necessarily any equivalents. I don't know of any "emergency wrapping" on Apple platforms. It sounds like you would want either kCTLineBreakByCharWrapping or kCTLineBreakByClipping. If you don't want default wrapping, there are only so many ways not to do it.

Based on the number of problems reported in the In App Forum....absa****inglutely not!If that were the basis for making decisions, then we should not:notarize software,use dylibs,submit apps,purchase apple developer accounts.